This repository has been archived by the owner on Aug 30, 2024. It is now read-only.
fix nf4 performance in hybrid CPU #120
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
airMeng
reviewed
Feb 5, 2024
|
Please remember to use int4 config as default when hybrid |
|
@yuchengliu1 Can you check whether the new thread pool dispatch all jobs to P cores if E cores have poor performance? |
|
f4 performance will be remeasured after #172. |
Some parallel created with schedule2D do not dispatch, such as parallel of PrologueA and MHA reorder |
@yuchengliu1 Just run benchmark. Focus on GEMM only. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Type of Change
Automatic modify the thread number and disable to run nf4 on E-core when inferencing nf4 model on hybrid CPU.
Quantizing to nf4 model on hybrid CPU will get a warning now.
Description
detail description
Issues: xxx
Expected Behavior & Potential Risk
the expected behavior that triggered by this PR
How has this PR been tested?
how to reproduce the test (including hardware information)
Dependency Change?
any library dependency introduced or removed